<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<html>
<head>
<!-- Copyright 1997 The Open Group, All Rights Reserved -->
<title>val</title>
</head><body bgcolor=white>
<center>
<font size=2>
The Single UNIX &reg; Specification, Version 2<br>
Copyright &copy; 1997 The Open Group

</font></center><hr size=2 noshade>
<h4><a name = "tag_001_014_2790">&nbsp;</a>NAME</h4><blockquote>
val - validate SCCS files (<b>DEVELOPMENT</b>)
</blockquote><h4><a name = "tag_001_014_2791">&nbsp;</a>SYNOPSIS</h4><blockquote>
<pre><code>

val -

val <b>[</b>-s<b>][</b>-m <i>name</i><b>][</b>-r <i>SID</i><b>][</b>-y <i>type</i><b>]</b><i> file</i>...
</code>
</pre>
</blockquote><h4><a name = "tag_001_014_2792">&nbsp;</a>DESCRIPTION</h4><blockquote>
The
<i>val</i>
utility determines if the specified
<i>file</i>
is an SCCS file meeting the characteristics specified
by the options.
<p>
</blockquote><h4><a name = "tag_001_014_2793">&nbsp;</a>OPTIONS</h4><blockquote>
The
<i>val</i>
utility supports the <b>XBD</b> specification, <a href="../xbd/utilconv.html#usg"><b>Utility Syntax Guidelines</b>&nbsp;</a> ,
except that the usage of the - operand
is not strictly as intended by the guidelines
(that is, reading options and operands from standard input).
The following options are supported:
<dl compact>

<dt><b>-m&nbsp;</b><i>name</i>
<dd>
Specify a
<i>name</i>,
which is compared with the SCCS
<b>%M%</b>
keyword in
<i>file</i>.
(See
<i><a href="get.html">get</a></i>).

<dt><b>-r&nbsp;</b><i>SID</i>
<dd>Specify a
<i>SID</i>
(SCCS Identification String),
an SCCS delta number.
A check is made to determine if the
<i>SID</i>
is ambiguous (for example,
<b>-r</b>1
is ambiguous because it physically does not exist but implies 1.1,
1.2, and so on, which may exist) or invalid (for example,
<b>-r</b>1.0
or
<b>-r</b>1.1.0
are invalid because neither case can exist as a valid delta number).
If the
<i>SID</i>
is valid and not ambiguous, a check is made
to determine if it actually exists.

<dt><b>-s</b>
<dd>Silence the diagnostic message normally
written to standard output for any
error that is detected while processing each named file on
a given command line.

<dt><b>-y&nbsp;</b><i>type</i>
<dd>Specify a
<i>type</i>,
which is compared with the SCCS
<b>%Y%</b>
keyword in
<i>file</i>.
(See
<i><a href="get.html">get</a></i>).

</dl>
<br>
</blockquote><h4><a name = "tag_001_014_2794">&nbsp;</a>OPERANDS</h4><blockquote>
The following operands are supported:
<dl compact>

<dt><i>file</i><dd>A pathname of an existing SCCS file.
If a single instance
<i>file</i>
is specified as -,
and if no options are specified,
the standard input is read:
each line is independently processed as if it were a
command-line argument list.
(However, the line is not subjected to any of the shell
word expansions, such as parameter expansion or quote removal.)

</dl>
</blockquote><h4><a name = "tag_001_014_2795">&nbsp;</a>STDIN</h4><blockquote>
The standard input is a text file used only when the
<i>file</i>
operand is specified as -.
</blockquote><h4><a name = "tag_001_014_2796">&nbsp;</a>INPUT FILES</h4><blockquote>
Any SCCS files processed are files of an unspecified format.
</blockquote><h4><a name = "tag_001_014_2797">&nbsp;</a>ENVIRONMENT VARIABLES</h4><blockquote>
The following environment variables affect the execution of
<i>val</i>:
<dl compact>

<dt><i>LANG</i><dd>Provide a default value for the internationalisation variables
that are unset or null.
If
<i>LANG</i>
is unset or null, the corresponding value from the
implementation-dependent default locale will be used.
If any of the internationalisation variables contains an invalid setting, the
utility will behave as if none of the variables had been defined.

<dt><i>LC_ALL</i><dd>
If set to a non-empty string value,
override the values of all the other internationalisation variables.


<dt><i>LC_CTYPE</i><dd>
Determine the
locale for the interpretation of sequences of bytes of text data as
characters (for example, single- as opposed to multi-byte characters
in arguments and input files).

<dt><i>LC_MESSAGES</i><dd>
Determine the locale that should be used to affect
the format and contents of diagnostic
messages written to standard error.
and informative messages written to standard output.

<dt><i>NLSPATH</i><dd>
Determine the location of message catalogues
for the processing of
<i>LC_MESSAGES .
</i>
</dl>
</blockquote><h4><a name = "tag_001_014_2798">&nbsp;</a>ASYNCHRONOUS EVENTS</h4><blockquote>
Default.
</blockquote><h4><a name = "tag_001_014_2799">&nbsp;</a>STDOUT</h4><blockquote>
The standard output consists of informative messages
about either:
(1) each file processed, or;
(2) each command line read from standard input.
<p>
If the standard input is not used, for each
<i>file</i>
operand yielding a discrepancy,
the output line has the following format:
<p><code>
<tt>" %s: %s\n"</tt>, &lt;<i>pathname</i>&gt;,
&lt;<i>unspecified&nbsp;string</i>&gt;
</code>
<p>
If standard input is used,
a line of input is written before each of the preceding lines
for files containing discrepancies:
<p><code>
<tt>"%s:\n"</tt>, &lt;<i>input&nbsp;line</i>&gt;
</code>
</blockquote><h4><a name = "tag_001_014_2800">&nbsp;</a>STDERR</h4><blockquote>
Not used.
</blockquote><h4><a name = "tag_001_014_2801">&nbsp;</a>OUTPUT FILES</h4><blockquote>
None.
</blockquote><h4><a name = "tag_001_014_2802">&nbsp;</a>EXTENDED DESCRIPTION</h4><blockquote>
None.
<br>
</blockquote><h4><a name = "tag_001_014_2803">&nbsp;</a>EXIT STATUS</h4><blockquote>
The 8-bit code returned by
<i>val</i>
is a
disjunction of the possible errors, that is, it can be interpreted as
a bit string where
set bits are interpreted as follows:
<p><table <tr valign=top><th align=left>0x80
<th align=left>=
<th align=left>Missing file argument.
<tr valign=top><td align=left>0x40
<td align=left>=
<td align=left>Unknown or duplicate option.
<tr valign=top><td align=left>0x20
<td align=left>=
<td align=left>Corrupted SCCS file.
<tr valign=top><td align=left>0x10
<td align=left>=
<td align=left>Cannot open file or file not SCCS.
<tr valign=top><td align=left>0x08
<td align=left>=
<td align=left><i>SID</i> is invalid or ambiguous.
<tr valign=top><td align=left>0x04
<td align=left>=
<td align=left><i>SID</i> does not exist.
<tr valign=top><td align=left>0x02
<td align=left>=
<td align=left><b>%Y%</b>, <b>-y</b> mismatch.
<tr valign=top><td align=left>0x01
<td align=left>=
<td align=left><b>%M%</b>, <b>-m</b> mismatch.
</table>
<p>
Note that
<i>val</i>
can process two or more files on a given command line and can
process multiple command lines (when reading the standard input).
In these cases an aggregate code is returned:
a logical OR
of the codes generated for each command line and file processed.
</blockquote><h4><a name = "tag_001_014_2804">&nbsp;</a>CONSEQUENCES OF ERRORS</h4><blockquote>
Default.
</blockquote><h4><a name = "tag_001_014_2805">&nbsp;</a>APPLICATION USAGE</h4><blockquote>
Since the
<i>val</i>
exit status sets the 0x80 bit, shell applications checking
$?
cannot tell if it terminated due to a missing file argument or
receipt of a signal.
</blockquote><h4><a name = "tag_001_014_2806">&nbsp;</a>EXAMPLES</h4><blockquote>
In a directory with three SCCS files,
<b>s.x</b>
(of
<b>t</b>
type &quot;text&quot;),
<b>s.y</b>
and
<b>s.z</b>
(a corrupted file),
the following command could produce the output shown:
<pre>
<code>
val - &lt;&lt;EOF
-y source s.x
-m y s.y
s.z
EOF

-y source s.x

    s.x: %Y%, -y mismatch
s.z

    s.z: corrupted SCCS file
</code>
</pre>
<p>
</blockquote><h4><a name = "tag_001_014_2807">&nbsp;</a>FUTURE DIRECTIONS</h4><blockquote>
None.
</blockquote><h4><a name = "tag_001_014_2808">&nbsp;</a>SEE ALSO</h4><blockquote>
<i><a href="admin.html">admin</a></i>,
<i><a href="delta.html">delta</a></i>,
<i><a href="get.html">get</a></i>,
<i><a href="prs.html">prs</a></i>.
<br>
</blockquote><hr size=2 noshade>
<center><font size=2>
UNIX &reg; is a registered Trademark of The Open Group.<br>
Copyright &copy; 1997 The Open Group
<br> [ <a href="../index.html">Main Index</a> | <a href="../xshix.html">XSH</a> | <a href="../xcuix.html">XCU</a> | <a href="../xbdix.html">XBD</a> | <a href="../cursesix.html">XCURSES</a> | <a href="../xnsix.html">XNS</a> ]

</font></center><hr size=2 noshade>
</body></html>
